Permission management of cloud-based documents

ABSTRACT

Disclosed herein are system, method, and computer program product embodiments for managing cloud-based document permissions. In an embodiment, a document generation system may generate and/or store a cloud-based document. The document generation system may also generate links to the cloud-based document. The generated links may be associated with different permissions. For example, a first link may allow a first client device accessing the first link to edit the document while a second link may allow a second client device accessing the second link to only view the document. Other permissions may also include generating distinct graphical user interfaces (GUIs) associated with different links. The GUIs may accept input messages and/or comments in a chat panel. The document generation system may facilitate the delivery of these input messages to other client device with document access.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/637,762, filed Jun. 29, 2017, and is related to U.S. patentapplication Ser. No. 15/637,729, filed Jun. 29, 2017, entitled“Presentation Collaboration with Various Electronic Devices”, to U.S.patent application Ser. No. 15/637,096, filed Jun. 29, 2017, entitled“Color Theme Maintenance for Presentations”, to U.S. patent applicationSer. No. 15/637,077, filed Jun. 29, 2017, now issued as U.S. Pat. No.10,592,597, entitled “Smart Defaults Based On Previous Settings ForPresentation Slides”, and to U.S. patent application Ser. No.15/637,717, filed Jun. 29, 2017, entitled “Automatic Layout Engine” allof which are hereby incorporated by reference in their entireties.

BACKGROUND

As document creation evolves, writers, editors, and programmerssometimes collaborate with other contributors. To facilitatecollaboration between many contributors to the creation of a document,cloud-based document generation has become a common structure, allowingmany users to access and/or edit a document. In some instances,cloud-based documents may reside in a repository, allowing one user toaccess and/or edit the document at a time. For example, the cloud-baseddocument may implement a “check-out” featuring, allowing only one editorto make changes at a time. In other instances, some cloud-baseddocuments may allow real-time document editing.

As collaboration evolves, however, document owners may wish to segregateusers and grant different types of access to different individuals. Achallenge facing this segregation, however, is that the differentpermissions must be intuitive for the document owner to grant as well asintuitive for users to utilize.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are incorporated herein and form a part of thespecification.

FIG. 1 is a block diagram of a document permission management system,according to some embodiments.

FIG. 2 is a block diagram of a document permission management systemhighlighting distinct permissions, according to some embodiments.

FIG. 3A is a screen display of a document interaction graphical userinterface, according to some embodiments.

FIG. 3B is a screen display of a chat panel, according to someembodiments.

FIG. 4A is a screen display of an editor enabled graphical userinterface, according to some embodiments.

FIG. 4B is a screen display of a viewer enabled graphical userinterface, according to some embodiments.

FIG. 5 is an example computer system useful for implementing variousembodiments.

In the drawings, like reference numbers generally indicate identical orsimilar elements. Additionally, generally, the left-most digit(s) of areference number identifies the drawing in which the reference numberfirst appears.

DETAILED DESCRIPTION

Provided herein are system, apparatus, device, method and/or computerprogram product embodiments, and/or combinations and sub-combinationsthereof, for managing permissions associated with cloud-based documents.

The systems and methods described herein may manage, assign, and/ortransmit permission links associated with cloud-based documents. In anembodiment, a document generation system may generate and/or maintain adocument. The document may be a computer-readable document capable ofbeing displayed on a computer screen and/or a monitor. For example, thedocument may comprise text, an image, a spreadsheet and/or table, apresentation, a slideshow, computer program code, and/or an internetbrowser code. In an embodiment, the document may include transitoryinformation such as, for example, an audio and/or video file. Thedocument generation system may generate a document at the request of auser and/or a client device. The document generation system may alsostore the document in a repository internal to the document generationsystem.

In an embodiment, the document generation system may maintainpermissions associated with a generated document. The documentgeneration system may maintain permission based on different linksassociated with the document. A link may be, for example, a UniformResource Locator (URL), Uniform Resource Identifier (URI), and/or anembedded web object granting a client device access to a server and/ordatabase maintaining a document. The document generation system maygenerate unique links to a document and may transmit the unique links toclient devices. Each link may be associated with one or more uniqueidentification and unique permissions. If a client device utilizes thelink to access the associated document, the client device may receivethe permissions associated with the utilized link. This link structuremay allow the document generation system to grant different documentpermissions to different client devices.

In an embodiment, a link may include a unique identification. Thedocument generation system may format the link to include the uniqueidentification, by, for example, generating a unique textual URL. Thedocument generation system may transmit this link to a client device. Inan embodiment, the document generation system may maintain an index ofunique identifications and permissions associated with the unique linkidentifications. The permissions may include rights associated with acloud-based document. For example, the permissions may include allowinga client device that accesses the link to edit the associatedcloud-based document. In an embodiment, the link may not allow editingof the document but instead may allow a client device to view thedocument. In an embodiment, the link may allow commenting and/orinteracting with chat features associated with the document. In anembodiment, the commenting and/or chat interaction may be coupled withthe editor and/or viewer permission.

In an embodiment, client devices may share the link. Because thedocument generation system may associate permissions with a link, thelink may be shared among different client devices, granting other clientdevices the same associated permissions. For example, the link may beembedded in a webpage or sent via an electronic message, allowingmultiple client devices to access the link. In an embodiment, a sharedlink may still maintain a unique identification associated with thelink. If multiple client devices access the document using the samelink, the document generation system may still distinguish each clientdevice using a unique identifier, such as, for example, an InternetProtocol (IP) address associated with the client device. In anembodiment, although the document generation system may distinguish eachclient device, the document generation system may still grant the samepermissions to the client devices that access the document with the samelink.

In an embodiment, the document generation system may alter thepermissions associated with a link. The document generation system mayrevoke permissions and/or grant other permissions, enabling furtherinteractions with a document. This embodiment may allow for revocationof permissions to links that may be compromised and/or links that havebecome unsecure. This embodiment may also allow for enabling featuresfor a client device that has already received a link.

In an embodiment, a graphical user interface (GUI) display may be apermission associated with a link. For example, when a client deviceaccesses a link, the document generation system may generate a GUI,allowing the client device to interact with the document associated withthe link. The client device may display the GUI and/or send commands tothe document generation system using the GUI. In an embodiment, the GUImay display the link used to access the document, a document interfacefor interaction with the document, and/or a chat panel enabling chatfeatures.

In an embodiment, the GUI may display different elements depending onthe permissions associated with the link. For example, a client deviceaccessing a link with editor permissions may view a different GUI than aclient device accessing a link with viewer permissions. In anembodiment, a GUI associated with an editor permission may include adocument editing interface, an editor chat panel, and/or a viewer chatpanel. In an embodiment, a GUI associated with a viewer permission mayinclude a document viewing interface and/or a viewer chat panel.

A chat panel may be one or more sections of a GUI and/or may share theGUI's association with a document. The document generation system mayinstantiate the chat panel, receive comments and/or chat messages from aclient device via a chat panel, and/or maintain the comments and/or chatmessages in a repository. The client device may utilize the GUI totransmit comments and/or chat messages to the document generationsystem. In an embodiment, the document generation system may associatethe link used to access the document with a comment and/or chat messagereceived at a chat panel.

In an embodiment, the document generation system may generate a documentreference associated with the comment and/or chat message. The documentgeneration system may identify a parameter related to the document andassociate the parameter with the comment and/or chat message. Forexample, the document generation system may generate a presentation,including several presentation slides, and a link associated with thepresentation. The document generation system may transmit the link to aclient device, allowing the client device to access a GUI and interactwith the slides of the presentation. If the document generation systemreceives a comment from a client device while a slide is displayed onthe GUI, the document generation system may associate the slide numberof the displayed slide with the received comment. In an embodiment wherethe document is a text document including one or more pages, thedocument generation system may associate a page number of the displayedpage with the received comment.

In an embodiment, the document generation system may receive a commentassociated with a document from a first client device. The first clientdevice may interact with the document via a first GUI displayed on thefirst client device. The document generation system may store thereceived comment and/or associate a document reference to the comment.The document generation system may then receive a request to access thedocument from a second client device. The second client device may usethe same link as the first client device to access the document or mayuse a different link generated by the document generation system. Thedocument generation system may transmit a second GUI to the secondclient device. The second GUI may or may not display the same GUIcomponents as the first GUI. Using the second GUI, the second clientdevice may interact with the document and view the comment received fromthe first client device.

In an embodiment, if the document is a presentation, the comment mayinclude a slide number reference. When the second client device accessesthe presentation via the link, the second client device may interactwith the slides of the presentation via the second GUI. When the secondclient device views the slide associated with the comment, the documentgeneration system may transmit the comment to the second client device.The second GUI may display the comment when the second client deviceaccesses the slide associated with the comment. In an embodiment, thesecond GUI may display the comment in a chat panel. In an embodiment,the second GUI may not display the comment when the slide associatedwith the comment is not displayed on the second GUI.

In an embodiment, the chat panel associated with the second GUI mayutilize a notification feature to alert users of new comments and/orchat messages. For example, after a second client device accesses adocument with a comment and/or chat message, the document generationsystem may transmit to the second GUI a notification indicating that acomment and/or chat message is associated with the document that thesecond client device has not previously displayed. This notification mayinclude the comment, chat message, first client device identification,and/or document reference indicating a portion of the document to whichthe comment and/or chat message is applicable.

These features will now be discussed with respect to the correspondingfigures.

FIG. 1 is a block diagram of a document permission management system100, according to some embodiments. In an embodiment, documentpermission management system 100 may generate a cloud-based documentand/or manage links and permissions associated with the cloud-baseddocument. Document permission management system 100 may include documentgeneration system 110, network 120, and one or more client devices 130A,130B, . . . , 130 n.

In an embodiment, document generation system 110 may generate, store,and/or maintain cloud-based documents. Document generation system 110may also generate links associated with the cloud-based documents.Document generation system 110 may also assign permissions to the linksand/or maintain a record of the links and associated permissions.Document generation system 110 may include a server 111 and a documentdatabase 112.

In an embodiment, server 111 may comprise one or more processors,memory, routers, modems, antennae, and/or circuitry configured tointerface with document database 112, network 120, and/or a clientdevice 130. Server 111 may communicate with a client device 130 usingnetwork 120 and/or a network protocol. Network 120 may comprise anetwork capable of transmitting information either in a wired orwireless manner and may be, for example, the Internet, a Local AreaNetwork, and/or a Wide Area Network. The network protocol may be, forexample, a hypertext transfer protocol (HTTP), a TCP/IP protocol,Ethernet, or an asynchronous transfer mode. Server 111 may transmitand/or receive information to a client device 130. Server 111 mayprocess the information sent and/or received from a client device 130.Server 111 may retrieve information, such as, for example, documentproperties from document database 112 and/or transmit this informationto a client device 130. Server 111 may receive document interactionsand/or commands from a client device 130.

In an embodiment, server 111 may be configured to generate a cloud-baseddocument. The cloud-based document may comprise text, an image, aspreadsheet and/or table, a presentation, a slideshow, computer programcode, and/or an internet browser code. In an embodiment, the cloud-baseddocument may include transitory information such as, for example, anaudio and/or video file. Server 111 may interact with document database112 using a database management system and/or store a generatedcloud-based document in document database 112. Document database 112 maycomprise tables, records, indexes, and/or other memory configured tostore cloud-based documents and/or records pertaining to permissionsassociated with the cloud-based documents.

In an embodiment, server 111 may instantiate a cloud-based documentbased on a command received from a client device 130. Client device 130may be a computing platform, such as, but not limited to, a smartphone,tablet computer, laptop computer, desktop computer, web browser, and/orother computing device configured to connect to network 120 tocommunicate with document generation system 110. In an embodiment,server 111 may receive and/or store a document generated at a clientdevice 130. Server 111 may associate client device ownership of thedocument based on a property of the client device 130 that requestedgeneration of the document. For example, client device 130A may requestgeneration of a document. Client device 130A may provide accountinformation and/or log-in information to document generation system 110.In response to receiving account information and/or log-in information,document generation system 110 may allow client device 130A to generatea document. In an embodiment, server 111 may associate ownership of thedocument to client device 130A and/or an account associated with clientdevice 130A. In an embodiment, a user may utilize a different clientdevice 130 to access document generation system 110 and may still accessowned documents based on providing the same account information usinganother client device 130. In an embodiment, server 111 may storegenerated documents in document database 112 and/or maintain a record ofownership of the generated documents.

In an embodiment, the client device 130 and/or account that is deemedthe owner of a document may specify permissions associated with thedocument. An owner may utilize a client device 130 to interact withdocument generation system 110 to manage permissions associated with theowed document. In an embodiment, document generation system 110 mayreceive commands to generate one or more links to the document and/ortransmit the links to a client device 130. A link may be, for example, aUniform Resource Locator (URL), Uniform Resource Identifier (URI),and/or an embedded web object granting a client device 130 access to adocument stored in document generation system 110.

Document generation system 110 may generate unique links to a documentand may transmit the unique links to one or more client devices 130A,130B, . . . , 130 n. Each link may be associated with one or more uniqueidentifications and/or unique permissions. If a client device 130utilizes the link to access the associated document, the client device130 may receive the permissions associated with the utilized link fromdocument generation system 110. This link structure may allow documentgeneration system 110 to grant different document permissions todifferent client devices 130.

In an embodiment, a link may include a unique identification. Documentgeneration system 110 may format the link to include the uniqueidentification, by, for example, generating a unique textual URL.Document generation system 110 may transmit this link to a client device130. In an embodiment, client device 130A may send a command to documentgeneration system 110, causing document generation system 110 to send alink to client device 130B.

In an embodiment, document generation system 110 may maintain an indexof unique link identifications and/or permissions associated with theunique identifications. Document generation system 110 may store thisindex in document database 112 and/or in a separate memory storagedevice.

The associated permissions may include rights associated with acloud-based document. For example, permissions may include allowing aclient device 130 that accesses the link to edit the associatedcloud-based document. In an embodiment, the link may not allow editingof the document but instead may allow a client device 130 to view thedocument. In an embodiment, the link may allow commenting and/orinteracting with chat features associated with the document. In anembodiment, the commenting and/or chat interaction may be coupled withthe editor and/or viewer permission. Document permissions and chatfeatures will be further discussed with reference to FIGS. 3A-3B and4A-4B.

In an embodiment, a client device 130 with access to a link may sharethe link. Because document generation system 110 may associatepermissions with a link, the link may be shared among different clientdevices 130, granting other client devices 130 the same associatedpermissions. In an embodiment, client device 130A may receive a linkfrom document generation system 110. Client device 130A may thentransmit the link to one or more other client devices 130. For example,the link may be embedded in a webpage or sent via an electronic message,allowing multiple client devices 130 to access the link.

In an embodiment, a shared link may still maintain a uniqueidentification associated with the link. If multiple client devices 130access the document using the same link, document generation system 110may still distinguish each client device 130 using a unique identifier,such as, for example, an Internet Protocol (IP) address associated withthe client device 130, a phone number, Global Positioning System (GPS)information, account information, and/or other information capable ofdistinguishing client devices 130. In an embodiment, although documentgeneration system 110 may distinguish each client device 130, documentgeneration system 110 may still grant the same permissions to the clientdevices 130 that access the document with the same link.

In an embodiment, document generation system 110 may alter thepermissions associated with a link. Document generation system 110 mayrevoke permissions and/or grant other permissions, enabling furtherinteractions with a document. This embodiment may allow for revocationof permissions to links that may be compromised and/or links that havebecome unsecure. This embodiment may also allow for enabling featuresfor a client device 130 that has already received a link.

In an embodiment, a graphical user interface (GUI) display may be apermission associated with a link. For example, when a client device 130accesses a link, document generation system 110 may generate a GUI,allowing the client device to interact with the document associated withthe link. A client device 130 may display the GUI and/or send commandsto the document generation system using the GUI. In an embodiment, theGUI may display the link used to access the document, a documentinterface for interaction with the document, and/or a chat panelenabling chat features. The GUI display feature will be discussed infurther detail with reference to FIGS. 3A-3B and 4A-4B.

FIG. 2 is a block diagram of a document permission management system 200highlighting distinct permissions, according to some embodiments. In anembodiment, document permission management system 200 may include adocument generation system 210, network 220, and client devicescategorized into two categories: editor client devices 232A, 232B, . . ., 232 n and viewer client devices 234A, 234B, . . . , 234 n. Documentgeneration system 210 may comprise components similar to documentgeneration system 110 described with reference to FIG. 1 . Thesecomponents may include server 211 and document database 212, which maybe configured to operate in a similar manner to server 111 and documentdatabase 112 as described with reference to FIG. 1 . Network 220 maycomprise components similar to network 120 also described with referenceto FIG. 1 .

Editor client device 232A, 232B, . . . , 232 n and/or viewer clientdevice 234A, 234B, 234 n may be a computing platform, such as, but notlimited to, a smartphone, tablet computer, laptop computer, desktopcomputer, web browser, and/or other computing device configured connectto network 220 to communicate with document generation system 210. In anembodiment, editor client device 232A may comprise different hardwarefrom editor client device 232B. In an embodiment, editor client device232A may comprise the same hardware as editor client device 232B. In anembodiment, viewer client device 234A may comprise different hardwarefrom viewer client device 234B. In an embodiment, viewer client device234A may comprise the same hardware as viewer client device 234B. In anembodiment, editor client device 232A may comprise different hardwarefrom viewer client device 234A. In an embodiment, editor client device232A may comprise the same hardware as viewer client device 234A.

In an embodiment, editor client device 232A may differ from editorclient device 232B based on the link received from document generationsystem 210. Document generation system 210 may transmit a first link toeditor client device 232A and a second link to editor client device232B. Document generation system 210 may associate different permissionsto the first and the second link. Document generation system 210 mayassign permissions received from an owner of a document. In anembodiment, the first and second link may be associated with an editorpermission, allowing an editor client device 232 that interacts witheither the first or second link to edit the associated document. In anembodiment, permissions associated with the first link and the secondlink may be the same.

In an embodiment, permissions associated with the first link may differfrom the permissions associated with the second link. For example, wheneditor client device 232A utilizes the first link to interact with thedocument, document generation system 210 may allow editor client device232A to edit a portion and/or subset of the document. In contrast, wheneditor client device 232B utilizes the second link to interact with thedocument, document generation system 210 may allow editor client device232B to edit the entirety of the document. Editor client device 232B maygain editor rights to edit the full document while editor client device232A may gain editor rights to edit a portion of the document. Forexample, document generation system 210 may restrict editor clientdevice 232A to certain pages of a text document, certain slides of apresentation, certain segments of software code, certain portions of anaudio file, and/or certain portions of a video file.

In an embodiment, editor client device 232A may be able to view a viewerchat panel on a GUI display (as described with reference to FIG. 4A)while editor client device 232B may not view the viewer chat panel. Inan embodiment, editor client device 232A may be able to view an editorchat panel on the GUI display while editor client device 232B may notview the editor chat panel. Because document generation system 210manages permissions related to links sent to editor client devices 232,document generation system 210 may customize the permissions associatedwith each link. This customization may allow shared editing privilegesamong editor client devices 232 but may apply specific editingrestrictions to certain editor client devices 232. Customizable linkpermissions may allow for greater flexibility in managing cloud-baseddocument access.

Links sent to viewer client devices 234 may also include customizablepermissions. In an embodiment, document generation system 210 maytransmit a first link to viewer client device 234A and a second link toviewer client device 234B. The first and second link may be associatedwith a viewer permission, allowing a viewer client device 234 thatinteracts with either the first or second link to view the associateddocument. In an embodiment, permissions associated with the first linkand the second link may be the same.

In an embodiment, permissions associated with the first link may differfrom the permissions associated with the second link. For example, whenviewer client device 234A utilizes the first link to interact with thedocument, document generation system 210 may allow viewer client device234A to view a portion and/or subset of the document. In contrast, whenviewer client device 234B utilizes the second link to interact with thedocument, document generation system 210 may allow viewer client device234B to view the entirety of the document. Viewer client device 234B maygain viewer rights to view the full document while viewer client device234A may gain viewer rights to view a portion of the document. Forexample, document generation system 210 may restrict viewer clientdevice 234A to certain pages of a text document, certain slides of apresentation, certain segments of software code, certain portions of anaudio file, and/or certain portions of a video file.

In an embodiment, viewer client device 234A may be able to view a viewerchat panel on a GUI display (as described with reference to FIG. 4B)while viewer client device 234B may not view the viewer chat panel.Because document generation system 210 manages permissions related tolinks sent to viewer client devices 234, document generation system 210may customize the permissions associated with each link. Thiscustomization may allow shared viewing privileges among viewer clientdevices 234 but may apply specific viewing restrictions to certainviewer client devices 234.

In an embodiment, document generation system 210 may restrict the timeduring which a viewer client device 234 may view the document. Forexample, document generation system 210 may specify windows of time toallow and/or disallow access to a document. For example, a link sent toviewer client device 234A may allow viewer client device 234A to accessthe document between 3:00 PM and 4:00 PM. In an embodiment, this windowof time may correspond to a presentation of the document, such as, forexample, a slideshow presentation. In an embodiment, document generationsystem 210 may impose a time limit restriction on the link access to thedocument. For example, viewer client device 234A may be allowed to viewthe document for one hour starting from when viewer client device 234Afirst utilizes the link.

In an embodiment, document generation system 210 may place locationrestrictions on links sent to viewer client devices 234. For example,although viewer client device 234A may have access to a link, documentgeneration system 210 may require that viewer client device 234A belocated in a certain geographical location before providing access tothe document. In an embodiment, document generation system 210 mayrequire that viewer client device 234A provide a Global PositioningSystem (GPS) coordinate before granting access to the document. In anembodiment, document generation system 210 may determine a location ofviewer client device 234A based on an IP address of viewer client device234A.

The permissions described with reference to viewer client devices 234may also be applied to editor client devices 232.

In an embodiment, an editor client device 232 may differ from a viewerclient device 234 based on the link received from document generationsystem 210. For example, editor client device 232A may receive a firstlink from document generation system 210 with editor permissionsassociated with the first link. Viewer client device 234A may receive asecond link from document generation system 210 with viewer permissionsassociated with the second link. The first and second link may beassociated with the same document. In an embodiment, document generationsystem 210 may convert the permission associated with the first linkfrom an editor permission to a viewer permission or from a viewerpermission to an editor permission. Although an editor client device 232may already maintain possession of the link, based on the revocation ofeditor permissions, editor client device 232 may be converted to aviewer client device 234. Document generation system 210 may alter thepermissions associated with the link as a result of potential breach ofsecurity. In an embodiment, document generation system 210 may convertthe permission associated with the second link from a viewer permissionto an editor permission to easily and quickly grant editor access to aviewer client device 234, converting the viewer client device 234 intoan editor client device 232.

In an embodiment, even after an editor link has been received at aneditor client device 232, document generation system 210 may alter thepermissions associated with the link, granting and/or revokingpermissions. Document generation system 210 may also perform thiscustomization with a viewer link that has been received at a viewerclient device 234.

In an embodiment, document generation system 210 may transmit a firstlink to editor client device 232A and a second link to viewer clientdevice 234A. The first and second link may correspond to the samecloud-based document stored in document generation system 210. Whileviewer client device 234A may view the document, editor client device232A may continue to make edits to the document. In an embodiment,document generation system 210 may receive the edits from editor clientdevice 232A, update the stored cloud-based document, and/or transmit theedit to viewer client device 234A. In an embodiment, these edits may besent to viewer client device 234A in real-time or in near real-time. Inan embodiment, viewer client device 234A need not refresh the documentor re-request the document to view the updates. Similarly, anothereditor client device 232B may also access the document and view edits inreal-time. In another embodiment, document generation system 210 mayrequire viewer client device 234A and/or editor client device 232B torequest updates before sending updates.

In an embodiment, the document may be a presentation. Using an editorlink, editor client device 232A may edit the presentation to varyingstages of completion. In an embodiment, editor client device 232A mayalso own the presentation, allowing editor client device 232A to dictatethe permissions related to the presentation. Editor client device 232Amay send a command to document generation system 210 to generate anothereditor link for editor client device 232B. Document generation system210 may generate the link and send the link to editor client device232B. In an embodiment, document generation system 210 may generate thelink for editor client device 232A. Editor client device 232A may thensend the link to editor client device 232B. After receiving the editorlink, editor client device 232B may edit the presentation. In anembodiment, editor client device 232B may access the presentation whileeditor client device 232A is also accessing the presentation. Thisembodiment may allow editor client device 232A and 232B to edit thepresentation simultaneously and in real time.

In an embodiment, editor client device 232A may send a command todocument generation system 210 to generate a viewer link for viewerclient device 234A. Document generation system 210 may generate the linkand send the link to viewer client device 234A. In an embodiment,document generation system 210 may generate the link for editor clientdevice 232A. Editor client device 232A may then send the link to viewerclient device 234A. After receiving the viewer link, viewer clientdevice 234A may view the presentation even while editor client device232A and/or 232B are still editing the presentation. In a presentationcontext, if a change is needed while the presentation is beingdelivered, editor client device 232A and/or 232B may edit thepresentation quickly, without the need to interrupt the flow of thegiven presentation and/or without the need to re-deliver an updatedpresentation file. In an embodiment, editor client device 232A and/orthe owner of the presentation may dictate the portions of thepresentation seen by viewer client device 234A. The ability to controlportions of a document viewed by a viewer client device 234 may alsoapply to other document types and may also be changeable in real-time bythe document owner.

In an embodiment, this configuration allows editor client device 232Aand/or a document owner to quickly generate a viewer link for apresentation. A document owner may transmit this link to efficientlydeliver presentation slides to one or more viewer client devices 234. Inan embodiment, because the document owner and/or editor client device232A may also manipulate the portions of the presentation seen by viewerclient devices 234, the document owner and/or editor client device 232Amay utilize the presentation slides as a customizable visualizationtool. This configuration may allow for cross-platform presentationsusing viewer links. In an embodiment, this configuration may remove thenecessity for a document owner to export and/or send a presentationfile. In an embodiment, this configuration may also remove the necessityfor a document owner to share the document owner's computer screen,which may display private information other than the presentation. Thedocument link configuration may allow for faster deployment of documentssuch as, for example, presentations. These permissions and control overviewer document interaction may also be applicable to the otheraforementioned document types.

FIG. 3A is a screen display of a document interaction graphical userinterface (GUI) 300, according to some embodiments. A documentgeneration system may instantiate document interaction GUI 300 and/orprovide access to document interaction GUI 300 to a client device.Document interaction GUI 300 may be developed using an applicationprogramming interface (API). In an embodiment, the document generationsystem may transmit permission associated link 310 to a client device,allowing the client device to access a document. Document interactionGUI 300 may be displayed on the client device, allowing the clientdevice to interact with the document.

In an embodiment, document interaction GUI 300 may comprise a permissionassociated link 310, a document interface 320, and/or a chat panel 330.A client device utilizing permission associated link 310 may access thedocument using, for example, a web browser. In an embodiment, after theclient device obtains permission associated link 310, the client devicemay utilize the link in a web browser to request the page and/ordocument associated with permission associated link 310. In anembodiment, permission associated link 310 may include a page addressand/or may be an HTTP request. Utilizing permission associated link 310may cause permission associated link 310 to appear in documentinteraction GUI 300.

If a document generation system receives an access request, documentgeneration system may return to the requesting client device one or morefiles, such as, for example, an HTML, file, images, flash files,JavaScript files, CSS files, audio files, video files, and/or otherfiles used to generate document interaction GUI 300.

Based on the files instantiated by the document generation system,document interaction GUI 300 may include document interface 320 and/orchat panel 330. In an embodiment, document interface 320 may display thedocument stored in the document generation system. Document interface320 may allow a client device displaying document interaction GUI 300 tointeract with the document. The available document interactions maydepend on the permission associated link 310 utilized to access thedocument. For example, if permission associated link 310 is associatedwith an editor permission, allowing a client device to edit thedocument, the client device may edit the document using documentinterface 320. For example, a client device may utilize computerperipherals, such as, for example, a mouse, keyboard, and/or touchscreen display to manipulate the document displayed in documentinterface 320. In an embodiment, the client device may transmit theseedits to the document generation system instantiating the document.

In an embodiment, if permission associated link 310 is associated with aviewer permission, allowing a client device to view the document, theclient device may view the document using document interface 320. In anembodiment, depending on the viewer permission associated withpermission associated link 310, document interface 320 may displayportions of the document. In an embodiment, the viewer permission mayallow the client device to navigate the full document using documentinterface 320. In an embodiment, the viewer permission may limit theportions of the document that the client device may navigate. Utilizingdocument interface 320, a client device may interact with a document.

Chat panel 330 will be described with reference to FIG. 3B. FIG. 3B is ascreen display of a chat panel 330, according to some embodiments. Chatpanel 330 may be a portion of document interaction GUI 300. In anembodiment, permission associated link 310 may allow commenting and/orinteracting with chat features associated with the document. In anembodiment, the commenting and/or chat interaction may be coupled withan editor and/or viewer permission.

Chat panel 330 may be one or more sections of document interaction GUI300 and/or may be associated with a document displayed in documentinterface 320. A document generation system may instantiate chat panel330, receive comments and/or chat messages from a client device via chatpanel 330, and/or maintain the comments and/or chat messages in arepository. The client device may utilize chat panel 330 to transmitcomments and/or chat messages to the document generation system. In anembodiment, the document generation system may associate permissionassociated link 310 with a comment and/or chat message received at chatpanel 330.

In an embodiment, client devices may submit input messages 333 to chatpanel 330. In an embodiment, input message 333 may include a textualmessage, image message, audio message, and/or video message. In anembodiment, if a client device is equipped with an input textperipheral, such as for example, a keyboard and/or a touch screendisplay, the client device may receive a textual input message 333. Inan embodiment, if a client device is equipped with a camera, the clientdevice may capture an image and/or video as an input message 333. In anembodiment, if a client device is equipped with a microphone, the clientdevice may capture an audio message as an input message 333. In anembodiment, chat panel 330 may display predefined input messages 333,allowing a client device to send a selection command as an input message333.

In an embodiment, when an input message 333 is received at chat panel330, the client device displaying document interaction GUI 300 maytransmit input message 333 to the document generation system. In anembodiment, document generation system may store input message 333and/or generate user message 331, associating input message 333 with auser identification 332 and/or a document reference 334. In anembodiment, the client device may generate the user message 331including the input message 333, user identification 332, and/ordocument reference 334. If the client device generates user message 331,the client device may transmit the message to the document generationsystem.

In an embodiment, to construct user message 331, the client deviceand/or the document generation system receiving input message 333 mayassociate user identification 332 and/or document reference 334 to inputmessage 333. User identification 332 may be an identification of theuser submitting input message 333. For example, user identification 332may be permission associated link 310, a portion of permissionassociated link 310, and/or an identification defined by the clientdevice, such as, for example, a selected display name submitted withinput message 333. In an embodiment, user identification 332 may includea location-based identification and/or a time-based identification, suchas, for example, a time stamp associated with the submission of inputmessage 333.

Document reference 334 may be a parameter related to the documentassociated with permission associated link 310. Document reference 334may refer to a portion of the document related to input message 333. Forexample, the document generation system may generate a presentation,including several presentation slides, and permission associated link310 associated with the presentation. The document generation system maytransmit the link to a client device, allowing the client device toaccess document interaction GUI 300 and interact with the slides of thepresentation. If the document generation system receives an inputmessage 333 from a client device while a slide is displayed on documentinteraction GUI 300, the document generation system may associate theslide number of the displayed slide with the input message 333. Documentreference 334 may include the displayed slide number. In an embodimentwhere the document is a text document including one or more pages, ifthe document generation system receives an input message 333 from aclient device while a page is displayed on document interaction GUI 300,the document generation system may associate the page number of thedisplayed page with the input message 333. Document reference 334 mayinclude the displayed page number.

In an embodiment, the document generation system may associate usermessage 331 to the document associated with permission associated link310. When another client device accesses the document, the client devicemay display a separate instance of chat panel 330, which may display thestored user message 331. For example, a first client device may beassociated with user message 331A. A second client device may view usermessage 331A and/or may submit input message 333B to generate usermessage 331B.

In an embodiment, chat panel 330 may include a notification feature toalert users of new user messages 331. For example, after a client deviceaccesses a document with an associated user message 331, the documentgeneration system may transmit to the client device a notificationindicating that a new user message 331 has been associated with thedocument that the client device has not previously displayed. Thisnotification may be a user message 331 and may include an input message333, user identification 332, and/or document reference 334. In anembodiment, the notification may include different coloring amongdifferent user messages 331, an audio tone, and/or the presence of aseparate display element displayed on document interaction GUI 300.

FIG. 4A is a screen display of an editor enabled graphical userinterface (GUI) 400, according to some embodiments. In an embodiment,editor enabled GUI 400 may display an editor permission associated link410, document editing interface 420, editor chat panel 430 and viewerchat panel 435. FIG. 4B is a screen display of a viewer enabledgraphical user interface (GUI) 405, according to some embodiments. In anembodiment, viewer enabled GUI 405 may display a viewer permissionassociated link 415, document viewing interface 425, and viewer chatpanel 435. Editor enabled GUI 400 and viewer enabled GUI 405 will bediscussed in conjunction to demonstrate contrasting embodiments.

A document generation system may instantiate editor enabled GUI 400and/or provide access to editor enabled GUI 400 to a client device. Thedocument generation system may also instantiate viewer enabled GUI 405and/or provide access to viewer enabled GUI 405 to a client device.Editor enabled GUI 400 and/or viewer enabled GUI 405 may be developedusing an application programming interface (API).

In an embodiment, the document generation system may transmit editorpermission associated link 410 to a first client device, allowing thefirst client device to access and/or edit a document. The documentgeneration system may associate editor permission associated link 410with editor permissions. When the first client device accesses editorpermission associated link 410, editor enabled GUI 400 may be displayedon the first client device, allowing the first client device to viewand/or edit the document.

In an embodiment, the document generation system may transmit viewerpermission associated link 415 to a second client device, allowing thesecond client device to view a document or a view a portion of thedocument. The document generation system may associate viewer permissionassociated link 415 with viewer permissions. When the second clientdevice accesses viewer permission associated link 415, viewer enabledGUI 405 may be displayed on the second client device, allowing thesecond client device to view the document.

Document editing interface 420 may be a portion of editor enabled GUI400. In an embodiment, document editing interface 420 may display adocument and/or allow editing of the document. This interaction mayoccur in a manner similar to the editing features described withreference to document interface 320 of FIG. 3A.

Document viewing interface 425 may be a portion of viewer enabled GUI405. In an embodiment, document viewing interface 425 may display adocument and/or portions of the document. Viewing the document may occurin a manner similar to the viewing permission features described withreference to document interface 320 of FIG. 3A.

In an embodiment, if a client device has accessed editor permissionassociated link 410 to view editor enabled GUI 400, the client devicemay also display editor chat panel 430 and viewer chat panel 435. In anembodiment, editor chat panel 430 may receive and/or display usermessages sent from other client devices that have accessed an editorpermission associated link 410. For example, if a first client devicehas accessed a first editor permission associated link 410 and hasgenerated an input message related to the underlying document, a secondclient device that has accessed a second editor permission associatedlink 410 may view the input message generated by the first clientdevice. In this embodiment, client devices with access to an editorpermission associated link 410 may communicate, adding comments andnotes concerning the document in editor chat panel 430.

In contrast, in an embodiment, viewer chat panel 435 may differ fromeditor chat panel 430. Viewer chat panel 435 may display user messagesand/or input messages related to the document from client devices thathave accessed a viewer permission associated link 415 as displayed inFIG. 4B. In an embodiment, viewer enabled GUI 405 may display viewerchat panel 435 but may not display editor chat panel 430. In anembodiment, a client device that utilizes viewer permission associatedlink 415 may not view editor chat panel 430. In an embodiment, thisconfiguration allows a client device with access to editor permissionassociated link 410 to view user messages and/or input messages from aclient device having access to viewer permission associated link 415. Inan embodiment, a document editor may view viewer comments regarding thedocument while the viewers may not view editor comments. In anembodiment, this configuration allows editors to communicate privatelyusing editor chat panel 430 without revealing the communications to aviewer having viewer permissions. This configuration may allow editorsto view viewer comments using viewer chat panel 435. In an embodiment,editor permission associated link 410 may allow an editor and/or aclient device to submit input messages and/or user messages to botheditor chat panel 430 and viewer chat panel 435. In this configuration,a client device utilizing editor permission associated link 410 may sendcommunications to client devices using viewer permission associated link415.

In an embodiment, while FIG. 4A displays editor chat panel 430 andviewer chat panel 435, editor enabled GUI 400 may display more than onecopy of editor chat panel 430 and viewer chat panel 435. For example,the document generation system may instantiate multiple editor chatpanels and/or may segregate users of editor permission associated link410 into different chat panel categories. In an embodiment, userssubscribed to a chat panel may communicate with other users alsosubscribed to the same chat panel. In an embodiment, viewer chat panels435 may also be segregated into multiple viewer chat panel 435. A userwith access to viewer permission associated link 415 may be grouped withother users of viewer permission associated link 415. In an embodiment,a user accessing editor permission associated link 410 may also view oneor more viewer chat panels 435.

FIG. 5 is an example computer system 500 useful for implementing variousembodiments. Various embodiments of the disclosure may be implemented,for example, using one or more computer systems, such as computer system500 shown in FIG. 5 . One or more computer systems 500 (or portionsthereof) can be used, for example, to implement document generationsystem 110 and/or 210 of FIGS. 1 and 2 .

Computer system 500 can be any well-known computer capable of performingthe functions described herein.

Computer system 500 includes one or more processors (also called centralprocessing units, or CPUs), such as a processor 504. Processor 504 isconnected to a communication infrastructure or bus 506.

One or more processors 504 may each be a graphics processing unit (GPU).In an embodiment, a GPU is a processor that is a specialized electroniccircuit designed to process mathematically intensive applications. TheGPU may have a parallel structure that is efficient for parallelprocessing of large blocks of data, such as mathematically intensivedata common to computer graphics applications, images, videos, etc.

Computer system 500 also includes user input/output device(s) 503, suchas monitors, keyboards, pointing devices, etc., that communicate withcommunication infrastructure 506 through user input/output interface(s)502.

Computer system 500 also includes a main or primary memory 508, such asrandom access memory (RAM). Main memory 508 may include one or morelevels of cache. Main memory 508 has stored therein control logic (i.e.,computer software) and/or data.

Computer system 500 may also include one or more secondary storagedevices or memory 510. Secondary memory 510 may include, for example, ahard disk drive 512 and/or a removable storage device or drive 514.Removable storage drive 514 may be a floppy disk drive, a magnetic tapedrive, a compact disk drive, an optical storage device, tape backupdevice, and/or any other storage device/drive.

Removable storage drive 514 may interact with a removable storage unit518. Removable storage unit 518 includes a computer usable or readablestorage device having stored thereon computer software (control logic)and/or data. Removable storage unit 518 may be a floppy disk, magnetictape, compact disk, DVD, optical storage disk, and/any other computerdata storage device. Removable storage drive 514 reads from and/orwrites to removable storage unit 518 in a well-known manner.

According to an exemplary embodiment, secondary memory 510 may includeother means, instrumentalities or other approaches for allowing computerprograms and/or other instructions and/or data to be accessed bycomputer system 500. Such means, instrumentalities or other approachesmay include, for example, a removable storage unit 522 and an interface520. Examples of the removable storage unit 522 and the interface 520may include a program cartridge and cartridge interface (such as thatfound in video game devices), a removable memory chip (such as an EPROMor PROM) and associated socket, a memory stick and USB port, a memorycard and associated memory card slot, and/or any other removable storageunit and associated interface.

Computer system 500 may further include a communication or networkinterface 524. Communication interface 524 enables computer system 500to communicate and interact with any combination of remote devices,remote networks, remote entities, etc. (individually and collectivelyreferenced by reference number 528). For example, communicationinterface 524 may allow computer system 500 to communicate with remotedevices 528 over communication path 526, which may be wired and/orwireless, and which may include any combination of LANs, WANs, theInternet, etc. Control logic and/or data may be transmitted to and fromcomputer system 500 via communication path 526.

In an embodiment, a tangible apparatus or article of manufacturecomprising a tangible computer useable or readable medium having controllogic (software) stored thereon is also referred to herein as a computerprogram product or program storage device. This includes, but is notlimited to, computer system 500, main memory 508, secondary memory 510,and removable storage units 518 and 522, as well as tangible articles ofmanufacture embodying any combination of the foregoing. Such controllogic, when executed by one or more data processing devices (such ascomputer system 500), causes such data processing devices to operate asdescribed herein.

Based on the teachings contained in this disclosure, it will be apparentto persons skilled in the relevant art(s) how to make and useembodiments using data processing devices, computer systems and/orcomputer architectures other than that shown in FIG. 5 . In particular,embodiments may operate with software, hardware, and/or operating systemimplementations other than those described herein.

It is to be appreciated that the Detailed Description section, and notthe Abstract section, is intended to be used to interpret the claims.The Abstract section may set forth one or more but not all exemplaryembodiments as contemplated by the inventor(s), and thus, are notintended to limit the disclosure or the appended claims in any way.

While the disclosure has been described herein with reference toexemplary embodiments for exemplary fields and applications, it shouldbe understood that the scope of the disclosure is not limited thereto.Other embodiments and modifications thereto are possible, and are withinthe scope and spirit of the disclosure. For example, and withoutlimiting the generality of this paragraph, embodiments are not limitedto the software, hardware, firmware, and/or entities illustrated in thefigures and/or described herein. Further, embodiments (whether or notexplicitly described herein) have significant utility to fields andapplications beyond the examples described herein.

Embodiments have been described herein with the aid of functionalbuilding blocks illustrating the implementation of specified functionsand relationships thereof. The boundaries of these functional buildingblocks have been arbitrarily defined herein for the convenience of thedescription. Alternate boundaries can be defined as long as thespecified functions and relationships (or equivalents thereof) areappropriately performed. Also, alternative embodiments may performfunctional blocks, steps, operations, methods, etc. using orderingsdifferent than those described herein.

References herein to “one embodiment,” “an embodiment,” “an exampleembodiment,” or similar phrases, indicate that the embodiment describedmay include a particular feature, structure, or characteristic, butevery embodiment may not necessarily include the particular feature,structure, or characteristic. Moreover, such phrases are not necessarilyreferring to the same embodiment. Further, when a particular feature,structure, or characteristic is described in connection with anembodiment, it would be within the knowledge of persons skilled in therelevant art(s) to incorporate such feature, structure, orcharacteristic into other embodiments whether or not explicitlymentioned or described herein.

The breadth and scope of disclosed inventions should not be limited byany of the above-described exemplary embodiments, but should be definedonly in accordance with the following claims and their equivalents.

What is claimed is:
 1. A system, comprising: a memory; and one or moreprocessors, coupled to the memory, configured to perform operationscomprising: receiving, from a client device, a request to access adocument associated with a link, wherein: a permission for the clientdevice to access the document is embedded in the link: the permissionincludes a first access permission and a second access permissiondifferent from the first access permission; the first access permissioncomprises displaying a first chat panel including a first comment to thedocument and a second chat panel including a second comment to thedocument; and the second access permission comprises concealing thefirst chat panel and displaying the second chat panel; and responsive toreceiving the request to access the document associated with the link:causing display, on the client device, of the document concurrently withthe first and second chat panels associated with the document responsiveto the link having the first access permission, wherein the first chatpanel includes at least one of messages from users associated with thedocument or edits made to the document; and causing display, on theclient device, of the document while concealing the first chat panel anddisplaying the second chat panel responsive to the link having thesecond access permission.
 2. The system of claim 1, wherein theoperations further comprise causing concurrent display, on the clientdevice, of the document and a plurality of chat panels associated withthe document responsive to the link having a third access permissiondifferent from the first and second access permissions, wherein theplurality of chat panels includes the first chat panel.
 3. The system ofclaim 1, wherein the operations further comprise: receiving, from a userhaving the first access permission, a comment to the document via thefirst chat panel; and storing the comment in a database.
 4. The systemof claim 3, wherein the operations further comprise generating anotification in response to receiving the comment.
 5. The system ofclaim 1, wherein the operations further comprise granting rights to editthe document responsive to the link having the first access permission.6. The system of claim 5, wherein the operations further comprise:receiving, from a user having the first access permission, an edit tothe document; and storing the edit in a database.
 7. A non-transitorycomputer-readable device having instructions stored thereon that, whenexecuted by at least one computing device, cause the at least onecomputing device to perform operations comprising: receiving, from aclient device, a request to access a document associated with a link,wherein: a permission for the client device to access the document isembedded in the link; the permission includes a first access permissionand a second access permission different from the first accesspermission; the first access permission comprises displaying a firstchat panel including a first comment to the document and a second chatpanel including a second comment to the document; and the second accesspermission comprises concealing the first chat panel and displaying thesecond chat panel; and responsive to receiving the request to access thedocument associated with the link: causing display, on the clientdevice, of the document concurrently with the first and second chatpanels associated with the document responsive to the link having thefirst access permission, wherein the first chat panel includes at leastone of messages from users associated with the document or edits made tothe document; and causing display, on the client device, of the documentwhile concealing the first chat panel and displaying the second chatpanel responsive to the link having the second access permission.
 8. Thenon-transitory computer-readable device of claim 7, wherein theoperations further comprise causing concurrent display, on the clientdevice, of the document and a plurality of chat panels associated withthe document responsive to the link having a third access permissiondifferent from the first and second access permissions, wherein theplurality of chat panels includes the first chat panel.
 9. Thenon-transitory computer-readable device of claim 7, the operationsfurther comprising: receiving, from the client device having the firstaccess permission, a comment to the document via the first chat panel;and storing the comment in a database.
 10. The non-transitorycomputer-readable device of claim 9, the operations further comprisinggenerating a notification in response to receiving the comment.
 11. Thenon-transitory computer-readable device of claim 7, the operationsfurther comprising granting rights to edit the document responsive tothe link having the first access permission.
 12. The non-transitorycomputer-readable device of claim 11, the operations further comprising:receiving, from the client device having the first access permission, anedit to the document; and storing the associated edit in a database. 13.The non-transitory computer-readable device of claim 7, the operationsfurther comprising receiving a request to convert the permission of thelink from the first access permission to the second access permission orfrom the second access permission to the first access permission.
 14. Acomputer-implemented method, comprising: receiving, from a clientdevice, a request to access a document associated with a link wherein: apermission for the client device to access the document is embedded inthe link; the permission includes a first access permission and a secondaccess permission different from the first access permission; the firstaccess permission comprises displaying a first chat panel including afirst comment to the document and a second chat panel including a secondcomment to the document; and the second access permission comprisesconcealing the first chat panel and displaying the second chat panel;and responsive to receiving the request to access the documentassociated with the link: causing display, on the client device, of thedocument concurrently with the first and second chat panels associatedwith the document responsive to the link having the first accesspermission, wherein the first chat panel includes at least one ofmessages from users associated with the document or edits made to thedocument; and causing display, on the client device, of the documentwhile concealing the first chat panel and displaying the second chatpanel responsive to the link having the second access permission. 15.The computer-implemented method of claim 14, wherein the method furthercomprises causing concurrent display, on the client device, of thedocument and a plurality of chat panels associated with the documentresponsive to the link having a third access permission different fromthe first and second access permissions, wherein the plurality of chatpanels includes the first chat panel.
 16. The computer-implementedmethod of claim 14, further comprising: receiving, from the clientdevice having the first access permission, a comment to the document viathe first chat panel; and storing the comment in a database.
 17. Thecomputer-implemented method of claim 16, further comprising generating anotification in response to receiving the comment.
 18. Thecomputer-implemented method of claim 14, further comprising grantingrights to edit the document responsive to the link having the firstaccess permission.
 19. The computer-implemented method of claim 18,further comprising: receiving, from the client device having the firstaccess permission, an edit to the document; and storing the edit in adatabase.
 20. The computer-implemented method of claim 14, furthercomprising receiving a request to convert the permission of the linkfrom the first access permission to the second access permission or fromthe second access permission to the first access permission.